home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Shareware Overload Trio 2
/
Shareware Overload Trio Volume 2 (Chestnut CD-ROM).ISO
/
dir35
/
appnuke.zip
/
APPBAT.DOC
< prev
next >
Wrap
Text File
|
1993-09-10
|
5KB
|
96 lines
OK: hang on. This ain't rocket science. Since I dunno who will run in
to this, without seeing posts about it, There is an intro at the end.
Before unzipping NUKE.ZIP, be WARNED! this thing is a great powerful
little tool... it will delete a directory with it's subdirectories and
all files, including those that have cryptic names like "⌡╪⌠▐╕║ ". And,
moreover, should you goof up, UNDELETE WILL NOT WORK! nEIther will it
ask for comfirmation.... it just blows it all away.
The first thing to do is create a separate compression directory, that
will not have a lotta traffic to screw up that area of the FAT. as:
md C:\ZIPS
cd C:\ZIPS
[Better yet you could partition the drive]
change into the zip dir, and invoke your file compressor from there; as:
pkzip -a TERMCOMM.ZIP C:\BBS\*.*
the "-a" adds all the files in your termcomms directory, [e.g. BBS]
to termcomm.com.zip, which is now in your \zips\ dirctory.
Now, you need to create a ".bat" file that will create a directory,
unzip the app, [in this case your termcomm] into it, launch the
program, and when done modeming, (-u)pdate your logs, dialing dir,
etc., into your termcomm.zip, and clean up by removing all the
files and the directory. "APP.BAT" is a sample to do this.
the first line creates the directory...
md C:\BBS
the second moves into it...
cd C:\BBS
The third invokes pkunzip [which should be in your root or path] and
uncompresses all the related files into this directory.
The fourth launches the app.
The fifth line (-u)pdates any changed files [dialing dir & logs] in the .zip
BTW: if you get a disk error, "(r)etry (q)uit..." do CTRL-C, which will
abort the subsequent NUKE process, letting you save the dir as is.
The sixth line changes back to the root directory - you can't remove a
directory you are in.
The seventh line NUKES the directory
The eighth line invokes my directory menu program.
WHEREVER YOU SEE UPPER CASE, THE LETTERS MAY CHANGE DUE TO YOUR
PARTICULAR FILE, DRIVE, & DIRECTORY NAMES. lower case letters are
the commands that will be used in all instances except for pkzip..
which could be larc, pak, lzh, etc.
Although I named this "APP.BAT", typically I use just two letters to launch
the .bat file; thus "BB" at the dos prompt starts the termcomm. "DF" does
drafting, "BF" for bitfax, etc... Since I touch type, I can change and
launch a new app faster than anyone can drag a mouse over to an icon... A
touch typing program will increase your productivity more than anything else.
One last point: If you use a slower machine, check the docs on your data
compressor... it will have the switches to compress the files a little less for
FAST extraction [-e(x,n,f,s,0) with pkzip]. For example, you could set it up
to compress only the bulky txt & overlay files, and leave the binary "exe"
files alone for maximum launch speed on 286's.
INTRO
IF you find this setting in your HD sometime in the next few years, you may
not remember what it was put there for, or where it came from, or where to
put it now. Hopefully, this will help.
There have been a lotta posting about STACKER & DOUBLESPACE lately [aug 93]
on the bbs nets, and troubles that have been had with them. I asked if a data
compressor [e.g. pkzip] would not be better solution. Turns out even better
than I thought.
I've been told the former datacomps put everything into one looooooong file,
and much of the inherant DOS error checking is bypassed in favor of speed and
speedier, less robust, error traps. If this file header for your disk is hit,
the whole NINE yards is gone.
If instead, you packed the drive with a section of your apps compressed with
pkz, lhz, larc, pak or whatever, you had more options. Each app is it's own
file, and a FAT error will likely occur to one, [which will get your atttent-
ion] long before it blows the whole drive away.
Moreover, you could park the backup masters in their own directory and their
frequently changed data, graphic, or whatever modules in a separate directory.
Now: Since FAT errors occur during a "write", the directory that is currently
being written to is the one that is fried. Your master app, it's configs, and
whatever will still likely be all right. [partitioned drives]
Now, it has been a while since I looked at all the shareware data compressors,
but every one I can recall had the ability to compress for greater extraction
speed, or greater compression. If you have a slower machine, with very big
apps, you can choose to lightly compress, or not compress at all, binary [com
or exe] files which rarely compress enough to be worth it; instead compressing
only the menu overlays, .docs, text & dbf stuff....
Day Brown, DCPC, Box 9, Tilly AR 72679 (501)7456651, WWIV @8363 Fido 1:284/8